@title{TABLET}{Tablet/Digitizing Table Notes}
@keyword{Tablet Digitizing Digitising}
@index{Tablet Setup}
@index{Digitizing Tablet Setup Serial} 

 Digitizing tables (tablets) are used to physically point to a position (on 
 a flat map, for instance).  In PCI software, such applications include:  

 - vector digitization of maps, 
 - ground control point collection for image-to-map registration
 
 A tablet consists of a flat surface and a pointing device. Depending on
 the manufacturer and model, the surface can range from 12 inches by 12
 inches to 60 inches by 48 inches. 

 For PCI applications, a 16 button cursor is usually required. 

 The basic function of a tablet is to transmit the coordinate (position) of 
 the cursor back to the host computer.  PCI software generally supports 
 three modes:

 - Point mode: a coordinate is transmitted each time the user pushes a 
   button and releases it.  

 - Switch-Stream (track, intermittent) mode: coordinates are transmitted 
   continuously as a user holds down a button.

 - Stream (run) mode: coordinates are transmitted continuously, regardless 
   of whether a button is held down or not.  

 Most tablets have a physical resolution of 1000 lines per inch (40 lines per
 millimeter). 

 Note:  When PACE applications are run, they will automatically attempt to 
 set the tablet to a "known" state by using software commands.  This "known" 
 state may differ from the initial powerup state.  If other, non-PCI
 applications are run which require the tablet, it may be necessary to 
 power the tablet off and on again to restore the initial powerup state. 

 See Also: TBTEST, GCPWorks, GCIM, VECDIG

1	Connecting Tablets

 Tablets are usually designed to act in a manner similar to terminals. That 
 is, they are attached to RS-232C ports (terminal ports).

 Like other RS-232C devices, it is critical that the tablet and the port to 
 which it is connected be configured to allow communication. 

 Most tablets come with jumpers or toggle switches that give a range of 
 possible baud rates, parity, data bit size and stop bits. Check the 
 documentation for the tablet to find which characteristics can be changed 
 and how to interpret the current settings. In most cases the factory default 
 settings should be used with PCI software. 

 For most systems, two things have to be done to enable using a digitizing
 table:

  - Logins must be disabled on the port to which the tablet is connected.

  - Second, the port must be set to match the baud, parity, data bits and 
    stop bits of the tablet.

 Both of these are very dependent on the operating system involved, and on 
 the tablet to be used.

2	Summasketch
@keyword{Summasketch}
@index{Summasketch}

 The factory default setting is for the Summagraphics Summasketch to 
 transmit coordinates in packed binary mode.  However, PCI software
 requires the Summasketch to transmit coordinates in ASCII mode.
 Instructions for changing the appropriate jumpers are contained in the
 PCI Installation Guide for your computer.

 Note:  For Windows 3.1 only, when using the PACE programs GCIM and VECDIG,
 the tablet must be in packed binary mode.  However, when using GCPWorks
 for Windows 3.1, the tablet must be in ASCII mode.

 Proper communications settings for the SummaSketch with PCI software are
 as follows:

  9600 Baud
  Odd Parity
  8 data bits
  1 stop bit 

2	Micro-Grid II
@keyword{Micro-Grid II}
@index{Micro-Grid II}

 The  Summagraphics Micro-Grid II tablet comes in a  variety of sizes with 
 a 4 or 16 button puck (cursor).  The Microgrid is expected to be 
 transmitting in ASCII mode (default).  See the instructions that accompany 
 your Microgrid to ensure that it is set up to transmit properly.  Proper 
 communications settings for the Microgrid with PCI software are as follows:

  9600 Baud
  Odd Parity
  8 data bits
  1 stop bit 

2	IBM 5084
@keyword{IBM 5084}
@index{IBM 5084}

 NOTE:  This tablet is only supported on the IBM Risc System 6000 workstation
 under the AIX operating system.

 PCI software expects that data from the IBM 5084 is sent in Binary Data
 Format.  This format is the factory default.

2	GTCO DigiPad
@keyword{GTCO DigiPad}
@index{GTCO DigiPad}

 NOTE:  This tablet appears to belong to a family of tablets.  PCI has
 only tested the DigiPad 12.  From the documentation with the tablet, many 
 members of the family appear similar.

 These tablets are very flexible, and require the user to set them up prior 
 to use with the computer.  On the model 12, PCI software will work with 
 the number 12 and number 64 settings.  To set the tablet into the correct 
 mode on the model 12, choose the `S' on the superset menu, then `1' `2' or 
 `6' `4'.  These are associated with `ARC/INFO' from ERSI and ROCTEK 
 products respectively.

 Proper communications settings for the GTCO Digipad with PCI software are
 as follows:

  9600 Baud
  No Parity
  8 data bits
  1 stop bit 
  ASCII mode

2	Gentian/Altek
@keyword{Gentian Altek}
@index{Gentian}{Altek}

 On the Gentian (or Altek) logic board are switches which allow some 
 flexibility in selecting the communication characteristics.  Refer to 
 the manufacturer's documentation supplied with your Gentian.  PCI assumes 
 that the Gentian or Altek tablet has the standard firmware installed and 
 factory default settings in place.

 Proper communications settings for the Gentian with PCI software are as
 follows:

  9600 Baud
  Odd Parity
  7 Data Bits
  2 Stop Bits
  Report Format 1 (controlled on Logic Board)

2	CalComp 9100
@keyword{Calcomp 9100}
@index{Calcomp 9100}

 Using the Digitizer menu located on the CalComp, it is possible to set the 
 baud rate, parity, stop bits and data bits.  The installation/reference 
 manual supplied with your tablet gives more information on interpreting the 
 current settings and making modifications.  

 Please note: using a CalComp 9100 with a 4 or 12 button puck has not been
 fully tested, and is not guaranteed to work.

 If the tablet seems unresponsive, switch the power off and on again.  This 
 forces a hardware reset.

 Proper communications settings for the CalComp with PCI software are as
 follows:

  9600 Baud
  Odd Parity
  7 Data Bits 
  1 Stop Bit

2	CalComp 9500
@keyword{Calcomp 9500}
@index{Calcomp 9500}

 Using the Digitizer menu located on the CalComp, it is possible to set the 
 baud rate, parity, stop bits and data bits.  The installation/reference 
 manual supplied with your tablet gives more information on interpreting the 
 current settings and making modifications.  

 Proper communications settings for the CalComp with PCI software are as
 follows:

  9600 Baud
  Odd Parity
  7 Data Bits 
  1 Stop Bit. 

1	Communication Parameters

 Setting up communication between a computer and a tablet tends to
 vary extensively depending on the operating system in use.  In many
 cases, PCI attempts to handle the details of this; however, not all
 operating systems allow setting all the necessary parameters in a
 controlled manner.

 PCI software generally has the ability to set the baud, parity, data bits, 
 and stop bits for a port to which a tablet is connected, while the tablet 
 is being used.  Once the application completes, all settings revert to 
 their original state.  Some operating systems, however, require alternate
 methods of setting these parameters.  In all cases, users should examine
 the sections discussing System Specific setup to ensure all the correct
 steps are taken.

 PCI software will generally attempt to read the desired tablet settings
 out of the Parameter file (PRM.PRM), if one exists; or, in the case of
 windowing based software (such as GCPWorks), a control panel is displayed
 to the user to allow this configuration.  The rest of this section will
 discuss the setting of entries in the parameter file.  However, in the case
 of the windowing software control panel, the type of information set is
 the same; it is just achieved by selecting the appropriate values from
 various menus.

 The TB00, TB0: and TB0: parameters in the parameter file hold information 
 on the port name and configuration options.  When a PCI application is run, 
 these parameters are used to access the correct port and (optionally) modify 
 the baud, parity, data bits, and stop bits settings.

 Configuring these parameters is easiest done through the EASI procedure
 CONFIGUR, which provides a menu driven interface for setting device 
 parameters.  To run CONFIGUR, enter the following command at the EASI
 prompt (or select CONFIGUR from Xpace):

  EASI> r configur

 When the menu appears, select `D' for Digitizing Table, and change the 
 device name and configuration appropriately.

 To make the changes manually, enter the following commands at the EASI prompt:

   EASI> TB00 = "TB0:"
   EASI> TB0: = "actual_device_name"
   EASI> TB0# = type, baud, parity, data bits, stop bits

 where `actual_device_name' is the device name of the port to use on your
 system (e.g. /dev/tty01).

 The TB0# parameter values have the following definitions:

  type:           1:  ASCII Summagraphics Summasketch
                  3:  Gentian (Altek)
                  4:  CalComp 9100 (4 button)
                  5:  CalComp 9100 (12/16 button)
                  6:  Summagraphics Microgrid II
                  7:  CalComp 9500 (16 button)
  baud:           0:  Retain current baud rate
               9600:  Change to 9600 baud
  parity:         0:  Retain current parity
                  1:  Odd parity
                  2:  Even parity
                  3:  No parity
  data bits:      0:  Retain current number of data bits
                  7:  7 data bits
                  8:  8 data bits
  stop bits:      0:  Retain current number of stop bits
                  1:  1 stop bit
                  2:  2 stop bits

  For example:  TB0#=3,9600,1,7,2 would be for a Gentian tablet configured
                    for 9600 baud, odd parity, 7 data bits and 2 stop bits.  
                TB0#=7,0,0,0,0 would be for a CalComp 9500 series tablet where 
                    the port options already match the tablet, so no 
                    modifications have to be made. 

2	OSF/1 (Digital AXP)

 Digital AXP workstations usually come with two serial ports, (typically
 the device names are /dev/tty00 and /dev/tty01).  Users should note 
 that the first of these (/dev/tty00) is configured as a console 
 terminal/printer port and cannot be used as a normal serial port.  This
 usually limits digitizing tablets to being connected to the second port.

3	Disabling Logins

 To ensure that a login process (getty) is not running against the port for
 the digitizing table, search the file /etc/inittab for the line containing
 the terminal device name.   The line should look something like this:
 
  tty01:23:respawn:/usr/sbin/getty /dev/tty01 9600 vt100

 where /dev/tty01 is the port to which the table is connected.  Edit the 
 file, if necessary, commenting out the line (by placing a `#') at the
 beginning of it):
 
  #tty01:23:respawn:/usr/sbin/getty /dev/tty01 9600 vt100

 Next, you must force the initialization process to close and to open the 
 terminals according to the contents of the /etc/inittab file, by entering 
 the following command (note this must be done as root or superuser): 
 
  # /sbin/init  q

 Note:  This will NOT affect terminals which are already logged in, and
 therefore can be executed on a running system with active users. 
 The next time the system is booted the /etc/inittab file will be
 automatically referenced so the init command does not have to be reissued. 

3	Communication Parameters

 Setting communication parameters under OSF/1 should be done through PCI
 software as described in the general section, above.


2	OpenVMS (Digital AXP)

 Digital AXP workstations usually come with two serial ports, (typically,
 under OpenVMS, the device names are TTA0: and TTA1:).  Users should note 
 that the first of these (TTA0:) is configured as a console terminal/printer 
 port and cannot be used as a normal serial port.  This usually limits 
 digitizing tablets to being connected to the second port.

 Unlike on most systems, PCI's software does not change terminal port
 settings under OpenVMS.  To do so, the "SET TERMINAL" command is used.
 This allows setting of both the communications parameters, and disabling
 logins on the port.

 Additionally, the protection code on the port must be set to allow general
 users permission to access the port directly.  This is done using the
 ``SET PROTECTION'' command.

3	Port Settings

 The SHOW TERMINAL command can be used to check the current characteristics 
 of the device associated with the port.  The SET TERMINAL command can be
 used to change these characteristics to match them up with those of the 
 tablet.  The following list shows some of the more important characteristics 
 and the usual settings:

  $ SET TERMINAL characteristic term:

   Where `characteristic' is one of the following:

    Echoing:  Usually the host AXP echos any data       /NOECHO
    transmitted  to  it  back   along  the  line.
    Echoing must be disabled for tablets.

    Baud rates:  The  baud  rate  (usually  9600)       /SPEED=9600
    on  the line and for the tablet should match.

    Parity:  Tablets transmit  with even, odd,  or      /PARITY=EVEN
    no parity.  Most lines under  OpenVMS are set       /PARITY=ODD
    to no parity initially.                             /NOPARITY

    Eight bits:  Each character of data is sent as      /NOEIGHT
    either 7 bits or 8 bits.                            /EIGHT

    Type_ahead:  It is best to allow buffering of       /TYPE
    coordinates in the typeahead buffer.  

    Broadcasting:  It is best to  prevent  broad-       /NOBROADCAST
    casting  of messages  to the  tablet  in case
    they are interpreted as commands.

    Permanent:  This must be used to ensure  that       /PERMANENT
    changes  are  permanent.   This  may  require
    system manager privileges.

 Other settings should be left at the default values.

 The SET TERMINAL command is normally inserted into the system startup 
 command file, which is executed when the AXP system is rebooted.
 (The system startup command file is called: SYS$MANAGER:SYSTARTUP_VMS.COM)

3	Port Protection

 Setting the protection on the port is done by the command:

  $ SET PROTECTION=(S:RWLP,O:RWLP,G:RWLP,W:RWLP)/DEVICE term:

 As with the SET TERMINAL command, this too can be inserted into the
 system startup command file (SYS$MANAGER:SYSTARTUP_V5.COM).

3	Example

 The following shows an example output of the SHOW TERMINAL command for 
 a port configured for a Summagraphics Summasketch tablet:

  Terminal TTA1:, device type unknown, is online, record-oriented device, 
     carriage control.

     Error count                    0    Operations completed           28711
     Owner process                 ""    Owner UIC                      [PCI]
     Owner process ID        00000000    Dev Prot S:RWLP,O:RWLP,G:RWLP,W:RWLP
     Reference count                0    Default buffer size              255

  Terminal: _TTA1:      Device_Type: Unknown       Owner: No Owner
    Input:   9600     LFfill:  0     Width: 255     Parity: Odd
    Output:  9600     CRfill:  0     Page:   66     Terminate on parity errors
  Terminal Characteristics:
    Passall           No Echo            Type_ahead        No Escape
    No Hostsync       No TTsync          Lowercase         Tab
    No Wrap           Hardcopy           No Remote         Eightbit
    No Broadcast      No Readsync        No Form           Fulldup
    No Modem          No Local_echo      No Autobaud       No Hangup
    No Brdcstmbx      No DMA             No Altypeahd      Set_speed
    No Line Editing   Insert editing     No Fallback       No Dialup
    No Secure server  No Disconnect      No Pasthru        No Syspassword
    No SIXEL Graphics No Soft Characters No Printer Port   Application keypad
    No ANSI_CRT       No Regis           No Block_mode     No Advanced_video
    No Edit_mode      No DEC_CRT         No DEC_CRT2       No DEC_CRT3
    No DEC_CRT4

2	DG/UX (Data General AViiON)

 Each Data General AViiON typically comes with at least three serial ports.  
 The device names for the first three are /dev/tty00 for RS-232 A, 
 /dev/tty02 for RS-232 B, and /dev/tty01 for RS-232 C.

 If you are using a port other than one of these, contact your system
 manager to find out the device name.

 These serial ports come with 15-pin sockets, and are compatible with PC type
 15-pin to 25-pin adaptors.

3	Disabling Logins

 To ensure that a login process (getty) is not running against the port for
 the digitizing table, the serial ports will be examined using `sysadm'.

 To use `sysadm', log in as root and enter the command: sysadm  

 To examine the serial ports, go into the `ttymgmt' submenu and select the 
 `lstty' option.  
 
 If the serial port you wish to use is present (note /dev/tty01 is 
 `TTY 1'), and the State is `on', then it will be necessary to turn it off.

 To turn off getty for that serial port, enter the `modtty' option on
 the `ttymgmt' submenu, and change the logical state to a value of "off"
 while not changing any other values.

3	Port Protection

 Sometimes the serial port is write protected and normal users cannot
 read/write to it properly (though the superuser, or root can).  The port
 should be have full read/write access.  This can be done using the 
 following command (issued by root or superuser):
 
  # chmod 666 /dev/ttynn                (where nn is port number)

3	Communication Parameters

 Setting communication parameters under DG/UX should be done through PCI
 software as described in the general section, above.

2	HP/UX (Hewlett Packard 9000/7xx)

 Each HP 9000/7xx typically comes with at least two serial ports.  Normally, 
 a terminal device already exists for each serial port, and there is
 no need to create a new device.  Usually, the device name for `RS-232 1'
 is /dev/tty00, and for `RS-232 2' is /dev/tty01.  However, if these 
 terminal devices do not exist, they can be created using `sam', HP's 
 system management utility.  To use sam, you must log in as root or become 
 superuser, and enter the command: sam

3	Disabling Logins

 To ensure that a login process (getty) is not running against the port for
 the digitizing table, search the file /etc/inittab for the line containing
 the terminal device name.   The line should look something like this:
 
  a0:2:respawn:/etc/getty -h tty01 9600

 where tty01 is the port to which the table is connected.  Edit the 
 file, if necessary, commenting out the line (by placing a `#') at the
 beginning of it):
 
  #a0:2:respawn:/etc/getty -h tty01 9600

 Next, you must force the initialization process to close and to open the 
 terminals according to the contents of the /etc/inittab file, by entering 
 the following command (note this must be done as root or superuser): 
 
  # /etc/init  q

 Note:  This will NOT affect terminals which are already logged in, and
 therefore can be executed on a running system with active users. 
 The next time the system is booted the /etc/inittab file will be
 automatically referenced so the init command does not have to be reissued. 

3	Communication Parameters

 Setting communication parameters under HP/UX should be done through PCI
 software as described in the general section, above.

2	IRIX (Silicon Graphics Iris)

 Each SGI Iris comes with at least two serial ports.  The device names for 
 the first two are usually /dev/ttyd1 for port 1, and /dev/ttyd2 for port 2.

 If you are using a port other than one of these, contact your system
 manager to find out the device name.

 These serial ports come with 15-pin sockets, and are compatible with PC type
 15-pin to 25-pin adaptors.

3	Disabling Logins

 Disabling logins on the Iris is done by setting the serial port to `off' 
 through the System management utility under 4Dwm.  To do this you will 
 have to be the superuser or log in as root.   Turning the serial port 
 `off' does not mean it cannot be used, it merely prevents the Iris from 
 configuring it for a special purpose (e.g., modem or terminal).

 - Note: one option for this port that will be offered is `tablet'.  DO NOT
   select this option.

3	Communication Parameters

 Setting communication parameters under IRIX should be done through PCI
 software as described in the general section, above.

 - Note: SGI Iris systems are VERY sensitive to the number of stop-bits set.
   Most systems tend to ignore the number of stop-bits, but the Iris
   requires that these EXACTLY match what the tablet is set for.

2	PC Systems (Windows 3.1, NT and OS/2)

 Most PC systems have one or two serial ports.  Typically, the device names
 are COM1 and COM2.

 For Windows 3.1 systems only, the PACE programs GCIM and VECDIG 
 require the PCI provided driver called CDDRVR (Coordinate Digitizer Driver)
 to be installed.   However, the GCPWorks program does NOT require CDDRVR.
 CDDRVR does NOT have to be installed for Windows NT or OS/2 systems.

3	MODE Command

 For Windows 3.1 systems, the first command you must issue to enable tablet
 communication is the MODE command.  This ensures that the serial (COM) port
 to which the tablet is connected runs at the proper baud and is configured
 properly for your type of digitizing table.  The format of this line depends
 on the digitizing tablet being used.  This command should probably be added to
 your AUTOEXEC.BAT file.

3	CDDRVR Driver

 If you are using the GCIM or VECDIG programs on Windows 3.1 systems, you must
 also install the CDDRVR digitizing table driver.  The format of the CDDRVR
 command varies for each type of digitizing table.  You do NOT have to install
 CDDRVR is you are using GCPWorks instead of GCIM or VECDIG.

3	Summasketch

 The MODE and CDDRVR commands for a Summagraphics Summasketch tablet 
 connected to COM2: are as follows:

  MODE COM2:9600,O,8,1
  C:\PCI\DRI\CDDRVR.EXE /P/2

 Please note that unlike other systems, Windows 3.1 expects the Summasketch
 to be transmitting in Packed Binary format for the GCIM and VECDIG programs,
 not ASCII format.  Note:  GCPWorks uses ASCII format on all systems.

3	Gentian/Altek

 For a Gentian or Altek digitizing table configured with factory default 
 settings on COM2:, the following two lines properly set the Mode and 
 CDDRVR commands:

  MODE COM2:9600,O,7,2
  C:\PCI\DRI\CDDRVR.EXE /G/2

 For Gentian or Altek digitizing tables configured to be compatible with
 Autocad, use the following two lines:

  MODE COM2:9600,N,8,1
  C:\PCI\DRI\CDDRVR.EXE /G/2

3	CalComp 9500

 For a CalComp 9500 digitizing table on COM1:, use the following two lines:

  MODE COM1:9600,O,7,1
  C:\PCI\DRI\CDDRVR.EXE /E/1

2	AIX (IBM RISC System/6000)

 IBM RISC System/6000 workstations usually come with two serial ports, 
 (typically the device names are /dev/tty0 and /dev/tty1).

 All configuration of the serial ports is done using the `smit' system
 management utility.  This includes disabling logins and setting all the
 communications parameters for the port.

 If smit is not used to configure baud rate, parity, ... then it is
 possible to do this directly with PCI software; however, this is not 
 the recommended method, and some settings will have to be done using
 smit regardless. 

3	Using Smit

 Configuring the serial port is done using the system management utility
 smit when logged in as root or as superuser.  Serial ports are considered 
 to be `devices' of type `tty'.

 When changing the characteristics of the tty device, Logins should
 be set to `disabled'.  The BAUD rate, PARITY, BITS per character 
 (data bits) and number of STOPBITS should be changed to match the 
 hardware configuration of the tablet.  Changes to other settings
 may be required.

 One additional setting that is required is that the `STTY attributes
 for RUNTIME' must have `clocal' added to the list.

 It is recommended that interaction between the tablet and IBM RISC System
 6000 be tested to ensure proper data transmission before PCI software is 
 run.  Often this is possible by using the AIX (UNIX) cat command:

  % cat /dev/tty?       (where ? is the serial port number 0 or 1)

 When buttons are pressed on the digitizer cursor (puck) characters
 should appear on the terminal window.  If this happens, communication
 has been established (though it still may not be proper). 
 Use <Ctrl>-C to abort the the cat command.

 The PACE program TBTEST may also be of use.  This is run from EASI after
 some level of communication has been established.

2	SCO ODT (IBM PC)

 Most PC systems running SCO ODT have one or two serial ports, 
 (typically the device names are /dev/tty0 and /dev/tty1).

3	Disabling Logins

 To ensure that a login process (getty) is not running against the port for
 the digitizing table, search the file /etc/ttys for the line beginning
 with the terminal device name.   The first four entries on this
 line should be as follows:
 
  ttyn    none       unknown   off

 where ttyn is the port to which the table is connected.  Edit the file, if
 necessary, so that the port is defined as above. Next, you must force the
 initialization process to close and to open the terminals according to the
 contents of the /etc/ttys file, by entering the following command: 
 
  # kill  -HUP  1

 Note:  This will NOT affect terminals which are already logged in, and
 therefore can be executed on a running system with active users. 
 The next time the system is booted the /etc/ttys file will be
 automatically referenced so the kill command does not have to be reissued. 

3	Communication Parameters

 Setting communication parameters under ODT should be done through PCI
 software as described in the general section, above.

2	SunOS (Sun Sparcstation)

 Sun workstations usually come with at least two serial ports, (typically 
 the device names are /dev/ttya and /dev/ttyb).  

3	Disabling Logins

 To ensure that a login process (getty) is not running against the port for
 the digitizing table, search the file /etc/ttytab for the line beginning
 with the terminal device name.   This line should be entered in the file 
 as follows: 
 
  ttynn    none       unknown   off

 where ttynn is the port to which the table is connected. Edit the file, if
 necessary, so that the port is defined as above. Next, you must force the
 initialization process to close and to open the terminals according to the
 contents of the /etc/ttytab file, by entering the following command: 
 
  # kill -HUP 1

 Note:  This will NOT affect terminals which are already logged in, and
 therefore can be executed on a running system with active users. 

 The next time the system is booted the /etc/ttytab file will be
 automatically referenced so the kill command does not have to be 
 reissued. 

3	Communication Parameters

 Setting communication parameters under SunOS 4.1.X should be done through 
 PCI software as described in the general section, above.

2	Solaris (Sun Sparcstation)

 Sun workstations usually come with at least two serial ports, (typically 
 the device names are /dev/ttya and /dev/ttyb).  

3	Disabling Logins

 To ensure that a login process (ttymon) is not running against the port for
 the digitizing table, search the file /etc/inittab for the line containing
 the terminal device name and ttymon.  Edit the file and comment out
 this line by putting a `#' at the beginning of it.

 Next, you must force the initialization process to close and to open the 
 terminals according to the contents of the /etc/inittab file, by entering 
 the command:

  # init  q

 Note:  This will NOT affect terminals which are already logged in, and
 therefore can be executed on a running system with active users.
 The next time the system is booted the /etc/inittab file will be
 automatically referenced so the init command does not have to be 
 reissued.

3	Communication Parameters

 Setting communication parameters under Solaris 2.2 should be done through 
 PCI software as described in the general section, above.

2	Ultrix (Digital DECstation)

 DECstation workstations usually come with two serial ports, (typically the
 device names are /dev/tty00 and /dev/tty01). 

3	Disabling Logins

 To ensure that a login process (getty) is not running against the port for
 the digitizing table, search the file /etc/ttys for the line beginning
 with the terminal device name.   The first four entries on this
 line should be as follows:
 
  ttynn    none       unknown   off

 where ttynn is the port to which the table is connected. Edit the file, if
 necessary, so that the port is defined as above. Next, you must force the
 initialization process to close and to open the terminals according to the
 contents of the /etc/ttys file, by entering the following command: 
 
  # kill  -HUP  1

 Note:  This will NOT affect terminals which are already logged in, and
 therefore can be executed on a running system with active users. 
 The next time the system is booted the /etc/ttys file will be
 automatically referenced so the kill command does not have to be 
 reissued. 

3	Communication Parameters

 Setting communication parameters under Ultrix should be done through PCI
 software as described in the general section, above.

2	VMS (Digital VAX)

 Digital VAX/VMS systems usually come with at least two serial ports, 
 (typically, under VMS, the device names are TTA0:, TTA1:, etc.).

 Unlike on most systems, PCI's software does not change terminal port
 settings under VMS.  To do so, the "SET TERMINAL" command is used.
 This allows setting of both the communications parameters, and disabling
 logins on the port.

 Additionally, the protection code on the port must be set to allow general
 users permission to access the port directly.  This is done using the
 "SET PROTECTION" command.

3	Port Settings

 The SHOW TERMINAL command can be used to check the current characteristics 
 of the device associated with the port.  The SET TERMINAL command can be
 used to change these characteristics to match them up with those of the 
 tablet.  The following list shows some of the more important characteristics 
 and the usual settings.

	$ SET TERMINAL characteristic term:

	where `characteristic' is one of the following:

    Echoing:  Usually the host VAX echos any data       /NOECHO
    transmitted  to  it  back   along  the  line.
    Echoing must be disabled for tablets.

    Baud rates:  The  baud  rate  (usually  9600)       /SPEED=9600
    on  the line and for the tablet should match.

    Parity:  Tablets transmit  with even, odd,  or      /PARITY=EVEN
    no parity.  Most lines under VMS are set            /PARITY=ODD
    to no parity initially.                             /NOPARITY

    Eight bits:  Each character of data is sent as      /NOEIGHT
    either 7 bits or 8 bits.                            /EIGHT

    Type_ahead:  It is best to allow buffering of       /TYPE
    coordinates in the typeahead buffer.  

    Broadcasting:  It is best to  prevent  broad-       /NOBROADCAST
    casting  of messages  to the  tablet  in case
    they are interpreted as commands.

    Permanent:  This must be used to ensure  that       /PERMANENT
    changes  are  permanent.   This  may  require
    system manager privileges.

 Other settings should be left at the default values.

 The SET TERMINAL command is normally inserted into the system startup 
 command file, which is executed when the VAX system is rebooted.
 (The system startup command file is called: SYS$MANAGER:SYSTARTUP_V5.COM

3	Port Protection

 Setting the protection on the port is done by the following command:

  $ SET PROTECTION=(S:RWLP,O:RWLP,G:RWLP,W:RWLP)/DEVICE term:

 As with the SET TERMINAL command, this too can be inserted into the
 system startup command file (SYS$MANAGER:SYSTARTUP_V5.COM).

3	Example

 The following shows an example output of the SHOW TERMINAL command for 
 a port configured for a Summagraphics Summasketch tablet:

  Terminal TTA1:, device type unknown, is online, record-oriented device, 
     carriage control.

     Error count                    0    Operations completed           28711
     Owner process                 ""    Owner UIC                      [PCI]
     Owner process ID        00000000    Dev Prot S:RWLP,O:RWLP,G:RWLP,W:RWLP
     Reference count                0    Default buffer size              255

  Terminal: _TTA1:      Device_Type: Unknown       Owner: No Owner
    Input:   9600     LFfill:  0     Width: 255     Parity: Odd
    Output:  9600     CRfill:  0     Page:   66     Terminate on parity errors
  Terminal Characteristics:
    Passall           No Echo            Type_ahead        No Escape
    No Hostsync       No TTsync          Lowercase         Tab
    No Wrap           Hardcopy           No Remote         Eightbit
    No Broadcast      No Readsync        No Form           Fulldup
    No Modem          No Local_echo      No Autobaud       No Hangup
    No Brdcstmbx      No DMA             No Altypeahd      Set_speed
    No Line Editing   Insert editing     No Fallback       No Dialup
    No Secure server  No Disconnect      No Pasthru        No Syspassword
    No SIXEL Graphics No Soft Characters No Printer Port   Application keypad
    No ANSI_CRT       No Regis           No Block_mode     No Advanced_video
    No Edit_mode      No DEC_CRT         No DEC_CRT2       No DEC_CRT3
    No DEC_CRT4

3	MODE Command

 The first command you must issue to enable tablet communication, is
 the MODE command.  This ensures that the serial (COM) port to which 
 the tablet is connected runs at the proper baud and is configured properly 
 for your type of digitizing table.  The format of this line depends on the
 digitizing tablet being used.  This command should probably be added to
 your AUTOEXEC.BAT file.

3	CDDRVR Driver

 In addition to issuing the proper Mode command, you must also install the 
 CDDRVR digitizing table driver.  As with the Mode command, the format of 
 the CDDRVR command varies for each type of digitizing table.


3	Summasketch

 The MODE and CDDRVR commands for a Summagraphics Summasketch tablet 
 connected to COM2: are as follows:

  MODE COM2:9600,O,8,1
  C:\PCI\DRI\CDDRVR.EXE /P/2

 Please note that unlike other systems, the PC expects the Summasketch
 to be transmitting in `Packed Binary' format, NOT `ASCII' format.

3	Gentian/Altek

 For a Gentian or Altek digitizing table configured with factory default 
 settings on COM2:, the following two lines properly set the Mode and 
 CDDRVR commands:

  MODE COM2:9600,O,7,2
  C:\PCI\DRI\CDDRVR.EXE /G/2

 For Gentian or Altek digitizing tables configured to be compatible with
 Autocad, use the following two lines:

  MODE COM2:9600,N,8,1
  C:\PCI\DRI\CDDRVR.EXE /G/2

3	CalComp 9500

 For a CalComp 9500 digitizing table on COM1:, use the following two lines:

  MODE COM1:9600,O,7,1
  C:\PCI\DRI\CDDRVR.EXE /E/1

1	Trouble Shooting

 The following are the most common problems encountered when using digitizing
 tablets.  Please note that some of these may be operating system specific
 and therefore may not be relevant to you.

2	Port incorrect

 It is possible that the tablet is connected to the incorrect port.  For 
 example, the user may think that the port (device) name is /dev/tty00 but 
 in fact the physical connections have been made to port /dev/tty01. 

2	Communications incorrect

 Double check the settings on the tablet and the line to ensure that the
 communications settings for the tablet and in the TB0# parameter in the
 parameter file match.  Please refer to the section on Communication
 Parameters and the section for your specific tablet, for more information. 

2	Cabling incorrect

 One of the most common problems, especially on initial configuration, is
 incorrect cabling.  Refer to the installation manual supplied by the
 manufacturer of the tablet and double check all connections.  A common 
 error that occurs is in the connection of the tablet to the serial line.  
 Often it is necessary to use a connector that flips pins 2 and 3 (receive 
 and send), called a "null modem". 

2	Tablet hung

 Occasionally tablets will "hang", that is, refuse to communicate.  Often 
 this can be cleared up by powering off the tablet, waiting a few seconds 
 then powering it back on. 

 For Summasketch tablets this is a common occurrence.  In this case, since 
 the older Summasketchs have no on/off switch, the power pack must be 
 physically unplugged and then plugged back in again after waiting 5 or so 
 seconds. 

2	Invalid serial port

 Some computer systems have serial ports dedicated to special purposes.  For
 example, the Digital AXP systems dedicate the first serial port as a
 console port, which then cannot be used by application software.  Please 
 check the system specific section for information on any such port
 limitations.
